-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feng Office: Update to v3.11.2.8 #5992
Conversation
4146415
to
00bd280
Compare
hey @hgy59, I was attempting to upgrade this package but ran into some problems with the installer. With the earlier package it seems the original contributor sent some arguments to a supplemental installer which automated the first three steps of the four step wizard. Running this with it's original setup I got the following in the installer log:
My assessment of this was that the PHP execution did not include the extensions that would normally be included with the FPM service and these needed to be manually included. In this state however the wizard was able to be manually run on launch of the web page and if you configured all the required fields the installation would complete. The app seemed to be fully functional (under DSM 7; haven't completed the DSM 6 stuff yet). I then modified the script to include the PHP extensions. While there were no longer errors in the install log, the service log spat out an HTML page (https://pastebin.com/RNrxGT3u), which contained the error:
Now I don't know if this is a warning or an error preventing setup but the webpage does not load after the installation is completed. This is unlike when the automatic setup was not working before. I am not sure what else can be done to resolve this other than requiring the user to just do all the wizard steps. The challenge with that is that the wizard often times out when the database is being setup and only after trying to load the webpage a few times does the interface come up. EDIT: Okay, I think I've solved it. In reviewing the webpage generated by the manual install most of the parameters were identical with the exception of Upon further examination, it seems that the second error encountered during the initial database setup persists across both DSM 6 and 7. However, it is now obscured within the |
e18dcd3
to
767c7ef
Compare
a3d4c60
to
2a340cc
Compare
@hgy59, I believe this package update is now complete. Let me know if you have any thoughts from your review. |
2a340cc
to
4654c7f
Compare
hey @moneytoo, as you were the original contributor to this package, I wondered if you had any thoughts on my proposed update? |
ac83182
to
e58329b
Compare
e58329b
to
a8e48c1
Compare
This reverts commit 4838bce.
I've completed testing of the new backup and restore as well as simulated an upgrade from v3.11.1.2 to v3.11.1.19. Overall things work well in DSM 7 but there was one exception for the upgrade process for DSM 6. In DSM 7, the service log for an upgrade on a backup restore shows the following:
However in DSM 6 for an upgrade on a backup restore we see the following:
When attempting a normal package upgrade we see a similar error with a bit more detail for DSM 6:
All the PHP extensions are properly enabled as far as I can tell and all other functions seem to work well. Unsure as to the specific reason this is an issue under DSM 6. |
@hgy59, I believe the update is now complete. During the process, I realized that the path validation functions, or any functions that used |
I've conducted a detailed investigation and manually performed an upgrade following the guidelines from the Feng Office upgrade documentation. The results are as follows:
Although an initial error occurs when updating the plugins during the upgrade process, they are successfully updated afterward using the second command. This aligns with the documentation, which states:
Therefore, the error reported in the DSM 6 service log during the upgrade is promptly resolved by the plugin update command within the script. |
Description
This PR contains the following:
Fixes #2348
Closes #4230
Checklist
all-supported
completed successfullyType of change